Customized, billing controlled call bridging system

ABSTRACT

Method and apparatus for providing customized, billing-controlled call bridging services through a bridging node which includes a node interface for connection through incoming and outgoing telephone trunks to a carrier switch of a public switched network, an audio peripheral for recording, playing, and analyzing audio signals, and a node controller for controlling operation of the node interface and the audio peripheral.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of application Ser. No. 08/444,571,filed on May 19, 1995, now U.S. Pat. No. 5,692,034, which is acontinuation of application Ser. No. 08/254,166, filed on Jun. 6, 1994,now U.S. Pat. No. 5,581,607, which is a continuation of Ser. No.07/861,630, filed on Apr. 1, 1992, now U.S. Pat. No. 5,355,403, which isa continuation-in-part of application Ser. No. 07/852,491, filed on Mar.16, 1992, now U.S. Pat. No. 5,317,627, which is a continuation ofapplication Ser. No. 07/591,047, filed on Oct. 1, 1990, now U.S. Pat.No. 5,113,430.

BACKGROUND OF THE INVENTION

The present invention relates generally to the field of audio responseautomation, and more specifically, to the field of providing customized,billing-controlled call bridging services.

It is considered well known that significant economic advantages canoften be realized by replacing manual systems with automated systemssince the cost of human labor is very high. In the telecommunicationsworld, human operators have long been vital links in completing certaintypes of calls, including collect calls, third-party calls, andperson-to-person calls. However, the high costs of human laborassociated with providing human operator assistance is very undesirablefor most telephone service carriers.

Also, it is often desirable to control call billing options in certaintypes of telephone customer environments. In the penal environment, forexample, the propensity for billing fraud, such as billing a call to anunauthorized number or credit account, is very high. In order to reducethe likelihood of billing fraud, it is frequently advantageous to permitinmates to make only collect calls. Many prior telephone systems handleall penal calls identically and tend to provide too much human operatorinvolvement or billing functionality for penal environments, thusfailing to take full advantage of the special needs and characteristicsof penal environments.

Since prisoners often have abundant amounts of free time on their hands,inmate telephone privileges frequently provide inmates withopportunities for making nuisance calls to other parties, as well as tothe live operators. Also, prison officials routinely need to recordtelephone conversations of selected prisoners. Few, if any, priortelephones systems provide features for effectively preventing nuisancecalls and recording selected prisoner conversations.

There is, therefore, a need in the industry for a customized,billing-controlled call bridging system which addresses these and otherrelated, and unrelated, problems.

SUMMARY OF THE INVENTION

Briefly described, the present invention includes, in its most preferredembodiment, a method and an apparatus for providing customized,billing-controlled call bridging services. The apparatus of thepreferred embodiment of the present invention is connected throughincoming and outgoing telephone trunks to a carrier switch of a publicswitched network and includes at least one bridging node which includesa node interface for interfacing to the carrier switch, an audioperipheral for recording, playing, and analyzing audio signals, and anode controller for controlling operation of the node interface and theaudio peripheral. The public switched network is configured to directcalls from a selected plurality of customer telephones to a first set ofinput ports on the node interface.

The method of the preferred embodiment of the present inventionincludes, with respect to a collect-call application for a penalenvironment, receiving an origination number and a destination numberafter a caller originates a long distance call from a customertelephone. The bridging node then generates input port identificationdata identifying the bridging node input port receiving the call andanalyzing the input port identification data to select and initiate acustomized, billing-controlled, collect-call bridging application.

Subsequently, the destination number and origination number are analyzedto configure the collect-call bridging application. Such analysisincludes verifying that the owner of the destination number has notprecluded requests for acceptance of collect-call charges. Theorigination number is also analyzed, subject toorigination-number-specific installation options, to configure thecollect-call bridging application to prompt the caller for a personalidentification number (PIN) which is checked against lists of validPIN's and used to compare the destination number to a list ofdestination numbers deemed permissible for a particular caller assignedto a particular PIN. Another configuration option includes giving acaller an opportunity to choose, for example, Spanish prompts.Furthermore, another configuration includes recording, or allowingreal-time monitoring, of an inmate's conversation with a destinationparty.

Upon successful analysis of the destination and origination numbers, thecaller is prompted by the bridging node for identification informationwhich is recorded by the bridging node. If no response is received, thecaller is prompted again and subsequently dropped by the bridging nodeif the caller remains silent. At no time is the caller connected to alive operator. Furthermore, the call is billing-controlled, thus thecaller is never given an opportunity to select alternate forms ofbilling.

Upon receipt and recording of identification information, thedestination number is called through a bridging node output port, andthe destination party is prompted to accept collect-call charges with aprompt including the recorded identification information. Thedestination party's response is analyzed for an indication ofacceptance, and the call is bridged upon acceptance of the charges. Ifno response is received from the destination party, the bridging nodeaccesses and bridges a live operator to elicit a response from thedestination party. The length of the call is monitored, and a calldetail record is generated by the node controller.

An alternate embodiment of the present invention includes a plurality ofbridging nodes distributed over a wide area, and the public switchednetwork is configured to direct calls to an alternate bridging node uponunavailability of a primary bridging node. In another alternateembodiment of the present invention, a central controller is connectedto the plurality of bridging nodes and provides diagnostic and nodeconfiguration alteration functions. In yet another alternate embodimentof the present invention, one central controller is used to replace allof the node controllers so that the central controller actively controlseach and every bridging node.

It is therefore an object of the present invention to provide anautomated telecommunication system which provides customized,billing-controlled call bridging services.

Another object of the present invention is to provide a call bridgingsystem which is connected, through both inbound and outbound telephonelines, to one carrier switch of a public switched network.

Yet another object of the present invention is to provide a callbridging system designed to address billing fraud and nuisance calls.

Still another object of the present invention is to provide a callbridging system which analyzes input port identification data,origination numbers, and destination numbers to select customized callbridging applications.

Still another object of the present invention is to provide an automatedmethod of bridging a collect-call which includes recording a caller'sname and prompting a destination party for acceptance of the chargeswith a prompt which includes the caller's name.

Still another object of the present invention is to provide a callbridging system which records conversations and provides controlledaccess to the recorded conversations.

Still another object of the present invention is to provide a callbridging system which includes a plurality of bridging nodes connectedthrough a public switched network which directs calls to secondary nodesupon unavailability of primary nodes.

Still another object of the present invention is to provide a callbridging system which provides voice messaging functions when callbridging is unsuccessful.

Other objects, features and advantages of the present invention willbecome apparent upon reading and understanding this specification, takenin conjunction with the accompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram representation of the physical domain of aCustomized, Billing-Controlled Call Bridging System and associatedcomponents, in accordance with the preferred embodiment of the presentinvention.

FIG. 2 is a block diagram representation of the node ARU of FIG. 1.

FIG. 3 is a block diagram representation of the node interface of FIG.1.

FIG. 4 is a block diagram representation of the node controller of FIG.1.

FIG. 5 is a block diagram representation of the program domain of thecall bridging system of FIG. 1.

FIGS. 6-9 are flow chart representations of steps taken by the system ofFIG. 1.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT

Referring now in greater detail to the drawings, in which like numeralsrepresent like components throughout the several views, FIG. 1 shows ablock diagram representation of the physical domain of a Call BridgingSystem 10 and associated components, in accordance with the preferredembodiment of the present invention. The call bridging system 10includes a bridging node 30 which includes a node interface 32, a nodeaudio response unit (ARU) 34, and a node controller 36. The nodeinterface 32 is connected through a network trunk group 22 to a carrierswitch 20 of a public switched network (PSN) 12. The node ARU 34 isconnected to the node interface 32 through an ARU trunk group 33 and tothe node controller 36 through an ARU control line 35. The nodecontroller 36 is connected to the node interface 32 through an interfacecontrol line 37 and to the PSN 12 through a controller access line 38.

An origination telephone 14, an access telephone 15, a destinationtelephone 16, an operator bank 17, and a remote information provider 18are also shown connected to the PSN 12. Although shown as a single box,the origination telephone 14 represents a plurality of customertelephones serving one or more customers at one or more locations.Likewise, the access telephone 15 and destination telephone 16 representpluralities of telephones. Operation of the elements 14-18 will bediscussed in greater detail below.

It should also be understood that the PSN 12 includes a great variety ofinterconnecting switches, including local exchange carrier centraloffices (LEC CO's), access tandems, and long distance carrier points ofpresence (LDC POP's). Examples of acceptable connection links betweenthe origination telephone 14 and the bridging node 30 include equalaccess lines traveling through LEC CO's, direct access lines, and800-number lines accessed through automatic dialers.

The trunk groups 22, 33 each represent a plurality of incoming andoutgoing trunks having pluralities of communication paths. One exampleof an acceptable trunk is the common T1 line. The ARU control line 35and the interface control line 37 are data lines. One example of anacceptable data line for the ARU control line 35 and the interfacecontrol line 37 is the common RS-232 line. The controller access line 38represents at least one ordinary telecommunication line which providesthe node controller 36 access to the PSN 12 without going through thenode interface 32. Furthermore, although only one node interface 32 andnode ARU 34 are shown included in the bridging node 30, it is understoodthat additional components are added to increase capacity of thebridging node 30.

Refer also to FIG. 2, which shows the node ARU 34 of the preferredembodiment of the present invention in greater detail. References tocomponents not appearing in particular Figures being described and nototherwise noted are understood to refer to FIG. 1. The node ARU 34includes an ARU interface 45, an ARU processor 46, a disk controller 47,an ARU disk 48, and an I/O controller 49, connected as shown. The ARU 34is an audio peripheral which, under the direction of the node controller36, records, plays, and analyzes audio signals, as is explained ingreater detail below. The ARU processor 46 controls the ARU interface45, disk controller 47, and ARU disk 48 in response to commands receivedthrough the I/O controller 49 and ARU control line 35 from the nodecontroller 36. The ARU interface 45 is capable of detecting andproducing dual tone multi-frequency (DTMF) signals and converting audiosignals between T1 and ARU disk 48 formats. One example of an acceptablenode ARU 34 is the BTIII from Perception Technology Corp. of Canton,Mass.

FIG. 3 shows a block diagram representation of the node interface 32 ofFIG. 1. The node interface 32 is shown including input ports 50, outputports 51, an interface processor 52, an I/O controller 53, a diskcontroller 54, and a disk 55, connected as shown. Regardless of theparticular connection link between the origination telephone 14 and thenode interface 32, the PSN 12 is configured to direct calls from theorigination telephone 14, through the PSN 12 and network trunk group 22,and to specific input ports 50 on the node interface 32. Operation ofthe node interface 32 is controlled by both the interface processor 52and the node controller 36, which sends commands through the interfacecontrol line 37 and the I/O controller 53. One example of an acceptablenode interface 32 is the SDS-1000 from Summa Four of Manchester, N.H.

Refer now to FIG. 4, which shows a block diagram representation of thenode controller 36 of FIG. 1. Node controller 36 is a fault tolerant,general purpose controller which offers utility grade service from aredundant architecture which is capable of processing many applicationssimultaneously. Two buses, A & B, are both connected to redundanthardware components, including I/O processors 62a & 62b, memorysubsystems 63a & 63b, and CPU subsystems 64a & 64b. I/O processors 62a &62b are both connected to communications subsystem 61 and disk subsystem66 through disk control subsystem 65. The ARU control line 35, interfacecontrol line 37, and control access line 38 are shown connected tocommunications subsystem 61. Terminal 60 is also shown connected tocommunications subsystem 61.

The redundant architecture of the node controller 36 ensures continuousapplication reliability and availability. If one component falls, itspartner component typically continues so that there are normally twocomponents performing the same function at the same time. Also, each CPUsubsystem 64a, 64b contains duplicate CPU's which process the same dataat the same time, thus a total of four processors typically work on thesame data at the same time. Logic comparators continually compare theresults of each processor. If the processors on a board disagree, thatparticular board is taken off line, an error signal is generated, andits partner component continues without any processing degradation.

The operation of each component of the node controller 36 is relativelystraight forward. CPU subsystems 64 provide processor functions; memorysubsystems 63 provide operating memory; and I/O processors 62 provideinput and output capabilities. Disk control subsystem 65 providescontrol of disk subsystem 64, which stores conventional operating systemprogramming and application programming. Terminal 60 provides humanaccess to node controller 36 through communications subsystem 61. Oneexample of an acceptable node controller 36 is the Stratus XA2000 model30 from Stratus Computer, Inc. of Marlboro, Mass.

FIG. 5 is a block diagram representation of the program domain of thecall bridging system 10 of the preferred embodiment of the presentinvention. In the preferred embodiment of the present invention, theprogramming domain represents programming found, in large part, on thenode controller 36. Running below virtual operating system 70 arebackground applications 72, interface server 74, and ARU server 72. Theinterface server 74 accesses an input port table 78 and a dialed numbertable 80. Both the interface server 74 and the ARU server 76 areconnected to a monitor application 82 and a bridge application 90. Theconnecting lines extending between the servers 74, 76 and applications82, 90 represent interprocess communication paths. Although representedas single applications, the applications 82, 90 represent pluralities ofcustomized applications running simultaneously on the node controller36. The monitor application 82 is shown having access to a password file84, a recorded file 85, and an on-line file 86. The bridge application90 is also shown having access to the recorded file 85 and the on-linefile 86. In addition, the bridge application 90 has access to anidentification (ID) table 91, an automatic number identification (ANI)table 92, a personal identification number (PIN) table 93, and adestination validator 95, which is shown having access to a blocked file97 and a remote file 98, located on the remote information provider 18(FIG. 1).

Background applications 72 include applications which provide serviceswhich include, without limitation: billing, testing, error detection,and error notification. Billing services accumulate and formattransaction records of each caller into appropriate billing formats foruse locally or by remote billing agencies, accessed through thecontroller access line 38 (FIG. 1). Testing services routinely testvarious components throughout the system, including each communicationpath connected to the bridging node 30. The error detection and errornotification services evaluate error signals received from variouscomponents and the testing services to identify the various types oferrors. Based on that information, appropriate service personnel arenotified of the error. Notification steps may include directing the nodeARU 34 and node interface 32 to call and announce to selected servicepersonnel appropriate error messages or accessing radio paging systemsto notify the service personnel.

The interface server 74 and ARU server 76 are multi-tasking,multi-threading processes which provide programming interfaces betweenapplications and the node interface 32 and node ARU 34, respectively.The node controller 36 utilizes servers and applications which referencefiles and tables during processing. Such a table-referencing methodenhances customization, facilitates programming changes, and increasessystem availability.

FIGS. 6-9 are flow chart representations of steps taken by the callbridging system 10 of the preferred embodiment of the present inventionwhen executing a billing-controlled, collect-call process, such as issuitable for many penal environments. Refer to previous Figures whenreferences are made to components previously discussed.

In FIG. 6, the collect-call bridging process is shown beginning in step100 when a caller, such as an inmate, uses a selected customer telephone14 to dial 0+(destination number). The directory number assigned to thedestination telephone 16 (and dialed by the caller) is referred toherein as the destination number, and the directory number assigned tothe calling telephone (origination telephone 14) is referred to hereinas the origination number. As configured, the PSN 12 routes the call tothe carrier switch 20. The carrier switch 20 then requests access to thebridging node 30 (step 102) by signalling over the network trunk group22 in a pre-defined format which is specific to a particularcommunication path leading into a particular input port 50. Severalacceptable protocols include Feature Group D, direct access lines (orequivalent), and 800-number access through a dialer. The Feature Group Dand dialer methods include supplying both the origination number anddestination number, whereas the direct access method only supplies thedestination number since the input port designation functions as anequivalent to the origination number for any direct access lines.

After the node interface 32 receives the request for access from thecarrier switch 20, the node interface 32 analyzes the data of therequest to determine if access should be granted (decision 104). In thepreferred embodiment of the present invention, the interface processor52 of the node interface 32 compares the data to configuration tablessaved on the disk 55 to determine if access is granted. If access is notgranted, the process is terminated (step 106), as is discussed ingreater detail below. If access is granted, the call is answered anddata is transferred from the node interface 32 to the node controller 36along the interface control line 37 (step 108). The transferred datacorresponds to the origination number, the destination number, and inputport identification data generated by the node interface 32.

As the node controller 36 receives the transferred data, the programdomain shown in FIG. 5 is accessed. The interface server 74 receives thetransferred data and compares the interface identification data to theinput port table 78 to select and initiate a customized application(step 110). If an input port 50 has been assigned to a particularapplication, such as a bridge application 90, the transferred data isthen passed to the application through interprocess communication.However, if an input port 50 receives calls for many differentapplications, such as one or more monitor applications 82, the interfaceserver 74 also references the dialed number table 80 to select aparticular application and pass thereto the transferred data. Acollect-call bridge application 90 is selected and initiated at step110.

The first steps of the bridge application 90 are to analyze theorigination number and destination number to further configure thebridge application 90 since, in addition to utilizing a plurality ofcustomized bridge applications 90 in the preferred embodiment of thepresent invention, one particular bridge application 90 is often used toservice a variety of different customers. According to the bridgeapplication 90, the origination number (also referred to as the ANI) isfirst checked (step 112) against the ANI table 92 to verify that the PSN12 and carrier switch 20 only direct calls from selected customerorigination telephones 14. If the origination number is invalid, thebridging node 30 plays an announcement to the caller which indicatesthat the caller's telephone cannot access the bridging node 30. Morespecifically, the node controller 36, under direction of the bridgeapplication 90, interface server 74, and ARU server 76, directs the nodeABU 34 to play a particular digitized message on one of thecommunication paths on the ARU trunk group 33 and directs the nodeinterface 32 to bridge that communication path with the communicationpath leading through the network trunk group 22 to the originationtelephone 14 so that the caller hears the announcement. The process isthen terminated at step 116.

If the ANI is valid, the destination number is checked (step 118)through the destination validator 95, which selectively accesses theblocked file 97 stored locally on the disk subsystem 66 (FIG. 4) and theremote file 98 stored remotely on the remote information provider 18(FIG. 1). The destination number is checked to verify that the owner ofthe destination number has not precluded calls from particularorigination telephones 14 (blocked file 97) or requests for acceptanceof collect-call charges (remote file 98). If the destination number isnot valid, an announcement is played to the caller indicating why thecall cannot be completed, and the process is terminated (steps 120,122).

If the destination number is valid, the bridge application 90 refers tothe ID table 91 to determine, also based on the origination number, ifspecial processing is required for this particular call, based onspecific installation options (steps 124, 126). Optional specialprocessing steps include prompting the caller for a personalidentification number (PIN) and checking the caller's response againstthe PIN table 93, which can be used to further limit access to thebridge node 30 and to further restrict a caller's use by allowingspecific callers access to a limited number of listed destinations.Another optional special processing routine includes giving a caller anopportunity to choose, for example, Spanish prompts. Yet another routineincludes recording, or allowing real-time monitoring, of an inmate'sconversation, as is discussed in greater detail below. In addition toperforming special processing at the time indicated by step 126, specialprocessing also refers to setting variables for optional processes whichare delayed until later stages of the bridge application 90.

Step 128 refers to prompting the caller for identification informationand recording the caller's response. More specifically, the nodecontroller 36 instructs the node interface 32 to connect an ARU trunkgroup 33 communication path to the caller's communication path on thenetwork trunk group 22 and instructs the node ARU 34 to play a promptrequesting the caller to speak his or her name and to record thecaller's response. If no response is received, the caller is promptedagain and subsequently dropped by the bridging node if the callerremains silent. Upon receiving and recording identification information,the caller is placed on hold (step 130).

Referring now to FIG. 7, in the next step of the bridge application 90(step 134), the bridging node 30 calls the destination number. The callis placed when the node controller 36 instructs the node ARN 34 totransmit the destination number through an output port of the nodeinterface 32 and the network trunk group 22 to the carrier switch 20.Although protocal-specific data may accompany the destination number,the bridging node 30 does not transmit destination-specific routinginstructions to the carrier switch 20 since the bridging node 30 doesnot utilize routing tables or files. The carrier switch 20, rather thanthe bridging node 30, then attempts to route the call to the destinationtelephone 16.

If there is no answer from the destination telephone 16, or if thedestination telephone 16 is busy, (step 136) the bridge application 90plays an appropriate "no answer" or "busy" message, respectively (steps138, 140). The caller is then given the option of leaving a message forthe destination party (steps 142-146). Voice messaging 146 includesrecording a message from the caller and attempting to deliver themessage to the destination party at at least one later point in time. Ofcourse, the message would not be delivered unless the destination partyaccepts the charges for the collect call and the voice messagingservice.

If the destination party answers the destination telephone 16, thebridge application elicits a response (step 148) from the destinationparty, as is shown in FIG. 8. An announcement is first played notifyingthe destination party that the caller is attempting to reach thedestination party through collect billing and requesting the destinationparty to indicate, through transmitting a DTMF digit, whether or not thedestination party will accept the charges. Such an announcement includesplaying the digitized caller's name and any other origination-specificinformation, such as the penal institution's name. If the destinationparty responds to the announcement of step 166, the process continues inFIG. 7.

However, if the destination party does not respond, the bridging node 30initiates a call to the operator bank 17 and bridges an operator ontothe destination party's communication path through the node interface 32(step 172). The operator manually elicits a response (step 174) from thedestination party. If the destination party needs the caller's namerepeated, (step 176, 178) the operator can signal the bridging node 30to play the digitized caller's name again. After receiving thedestination party's response regarding acceptance of the collect-callcharges, the operator signals an indication (step 180) back to thebridging node 30. The process then continues in FIG. 7.

If the destination party chooses not to accept the charges, theprocesses is terminated (step 152). If the destination party chooses toaccept the charges, the bridging node 30 plays a branding messagethanking the parties for using the bridging node 30 (step 154). The callis then bridged through the node interface 32 (step 156). As the call isbeing bridged, origination-specific special processing variables formonitoring the conversation are checked (step 158). Such steps includeaccessing the on-line file 86 to determine if any penal administratorsare holding to monitor the conversation, as is discussed in more detailbelow.

During the conversation, the bridge application 90 continually monitorsthe conversation to detect a disconnect in order to terminate the bridge(steps 160, 164). Also, additional origination-specific specialprocessing is optionally performed (step 162). Such special processingincludes limiting durations of calls or playing overlaying messages tothe parties advising them of the caller's identity and location.

The process of terminating a call involves several steps. First, allcommunication paths are closed which may still be open on any inbound oroutbound ports on the node interface 32 connected to either the networktrunk group 22 or the ARU trunk group 33 which have been associated withthis particular call. Then, a call detail record including the length ofthe call is created by the background application 72 and processed.Transmission of the billing records through the controller access line38 to a billing service optionally occurs immediately after each call oron a batch basis. Finally, optional special processing occurs, such assaving a recorded conversation and updating the recorded file 85.

FIG. 9 shows a flow chart representation of the process of accessing thebridge node 30 to monitor caller conversations, including monitoringpreviously-recorded conversations and on-line, real-time conversations.In the penal environment example, a prison administrator dials a bridgenode access number from an access telephone 15 (step 200). In steps verysimilar to those shown in FIG. 6, the carrier switch 20 requests accessto the bridge node 30 (step 202). If access is granted by the nodeinterface 32, (step 204) the origination number, dialed number(destination number), and input port identification data are transmittedto the node controller 36 (step 208). The interface server 74 thenreferences the input port table 78 and dialed number table 80 to selectand initiate a particular monitor application 82 (step 210).

The monitor application 82 then directs the ARU server 76 and interfaceserver 74 to direct the node ARU 34 and node interface 32, respectively,to prompt the administrator for a password, record the administrator'sresponse, and transmit the response back to the node controller 36 foranalysis. The node controller 36 analyzes the password response andcompares it to the password file 84 (step 212). If the password is notvalid, the process is terminated (steps 214, 216). If the password isvalid, the administrator is prompted to select on-line or recordedmonitoring. (step 218)

If the administrator selects on-line monitoring, the administrator isprompted for selection criteria to determine which types ofconversations are to be monitored (step 226). An administrator maychoose to monitor all calls from one or more origination telephones 14,to one or more destination telephones 16, by one or more callers withidentified by distinct PINs, or any combination thereof. After theadministrator selects the criteria, a flag is set in the on-line file 86which acts as a signal to all currently proceeding and future bridgeapplications 90 that an administrator desires to monitor certain typesof conversations (step 228). If a match is ever found, the appropriatebridge application 90 will create a bridge to allow the administrator tolisten to the conversation.

If the administrator selects recorded monitoring, the administrator isagain prompted for selection criteria (step 220). The monitorapplication 82 then accesses the recorded file 85 to determine if anyrecorded conversations match the selection criteria. If matches arefound, the monitor application directs the node ARU 34 to play theconversations to the administrator (step 222). After monitoring iscompleted, the application is terminated (step 224).

In an alternate embodiment of the present invention, a plurality ofbridging nodes 30 are distributed over a wide area, and the publicswitched network is configured to direct calls to an alternate bridgingnode 30 upon unavailability of a primary bridging node 30. In anotheralternate embodiment of the present invention, a central controller,similar to the node controller 36, is connected through a wide-areanetwork to the plurality of bridging nodes 30 and provides diagnosticand node configuration alteration functions. In yet another alternateembodiment of the present invention, one central controller is used toreplace all of the node controllers 36 so that the central controlleractively controls each and every bridging node over the wide areanetwork.

While the embodiments of the present invention which have been disclosedherein are the preferred forms, other embodiments of the apparatuses andmethods of the present invention will suggest themselves to personsskilled in the art in view of this disclosure. Therefore, it will beunderstood that variations and modifications can be effected within thespirit and scope of the invention and that the scope of the presentinvention should only be limited by the claims below.

I claim:
 1. Method of providing customized, billing-controlled,collect-call bridging services to callers calling from customertelephones, said method comprising the steps of:configuring a publicswitched network to direct calls from customer telephones to first inputports on a first node of a billing-controlled call bridging system;receiving an origination number and a destination number through aninput port after a caller dials a destination number on a first customertelephone assigned to the origination number; generating input portidentification data identifying the input port receiving the originationnumber and destination number; analyzing the input port identificationdata and the origination number to select, initiate, and configure acustomized, billing-controlled collect-call bridging application;prompting the caller for caller identification information; recordingthe caller identification information; calling the destination numberthrough an output port; prompting a destination party for acceptance ofcollect-call charges, including transmitting the caller identificationinformation; analyzing any response from the destination party to detectacceptance of collect-call charges; and bridging the input port to theoutput port to complete the call upon detection of acceptance of thecollect-call charges.
 2. The method of claim 1, further including thesteps of:monitoring the amount of time the call is bridged; andgenerating a call data record indicating the monitored amount of time.3. The method of claim 1, further including the step of recordingconversation occurring over the bridged connection.
 4. The method ofclaim 1, further including the step of configuring the public switchednetwork to direct to a second node of the call bridging system callsoriginally directed to the first node of the call bridging system uponunavailability of the first node of the call bridging system.
 5. Themethod of claim 1, wherein the step of prompting the caller for calleridentification information is prompting the caller for a personalidentification number.
 6. The method of claim 1, wherein the step ofanalyzing the input port identification data is analyzing an automaticnumber identification signal.